[Improve] Streamline DCG command approval - #1062
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
e655ee2 to
28fb788
Compare
3e1b109 to
5f6e0a8
Compare
28fb788 to
f7ae3cb
Compare
5f6e0a8 to
dd00d03
Compare
dd00d03 to
e996b73
Compare
edelauna
left a comment
There was a problem hiding this comment.
Had some comments related to implementation.
|
Addressed the implementation and coverage feedback in 900282f. DCG reads the persisted flag cheaply before approval, preserves deferred full-state loading, and covers allow and pending chat-row paths. |
edelauna
left a comment
There was a problem hiding this comment.
Thanks for addressing the feedback, approving - but still unclear on how you want to handle the design for a DCG blocked command: #1062 (comment)
What changed
Reads the persisted DCG setting without eagerly building full provider state, restores full state loading until after approval, and adds coverage for an allowed command continuing through execution and for command rows awaiting a decision.
Why this change was made
The DCG integration should avoid unnecessary state work on ordinary commands while preserving explicit approval for guarded commands. Closes #1058 and completes #1049.
Impact
Command approval remains responsive when DCG is disabled, while guarded-command behavior and denied-state rendering are covered more completely.
Related PRs